What are your thoughts on this???

--____SLUWYXMZMXGPNEOAPFOO____
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I have created a application generator creates the add, delete, change, =
view database code and ASP code that will work for classic ASP and SQL =
Server 2000. It has been an instrumental piece that has saved me NUMEROUS =
hours, all I have to do is give this application the fields, and viola... =
the ready working code is created.=20

Now my problem is the future. I've pondered the idea of re-creating it in =
..NET which I hope to do when I get proficient at it, but in the mean time, =
do you think there will be any harm in future development if the administra=
tive functions of a website system (add, delete, change fields) would =
function well in an environment that has .NET for the front end presentatio=
n. I'm thinking I can keep creating systems using the app generator, then =
just make the front end of the system, .NET'ified. THe only downfall is =
that the add, delete, change will be in classic ASP, but is that a =
downfall, and will classic ASP be around for awhile. Is this logical to =
you???

Thanks!

--____SLUWYXMZMXGPNEOAPFOO____
Content-Type: multipart/related; boundary="____AJSQVBTWFXNMADMCYVMR____"


--____AJSQVBTWFXNMADMCYVMR____
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable


>

Re: What are your thoughts on this???

Shawn Ferguson wrote:
> I have created a application generator creates the add, delete,
> change, view database code and ASP code that will work for classic
> ASP and SQL Server 2000.

Similar to Eli Robillard's GenericDB?

> It has been an instrumental piece that has
> saved me NUMEROUS hours, all I have to do is give this application
> the fields, and viola... the ready working code is created.
>
> Now my problem is the future. I've pondered the idea of re-creating
> it in .NET which I hope to do when I get proficient at it, but in the
> mean time, do you think there will be any harm in future development
> if the administrative functions of a website system (add, delete,
> change fields) would function well in an environment that has .NET
> for the front end presentation. I'm thinking I can keep creating
> systems using the app generator, then just make the front end of the
> system, .NET'ified. THe only downfall is that the add, delete,
> change will be in classic ASP, but is that a downfall, and will
> classic ASP be around for awhile. Is this logical to you???
>
> Thanks!
>
If your application generator creates code that
1. Uses sql statements rather than recordsets to maintain data, and
2. passes values to the database via parameters,
then good for you. I think you may be doing a little too much processing
in the ASP (unless you tweak the generated code to use stored
procedures), but at least it is secure and relatively efficient
(compared to using recordsets for data maintenance, that is).

However, if your generator generates dynamic sql statements*, or uses
recordsets for database maintenance (as GenericDB does) then frankly I
think it should be scrapped. i created my first ASP app using GenericDB
and wound up rewriting it due to performance reasons.

The paradigm in .Net is completely different, and frankly, you would be
reinventing the wheel. There are class generators already written that
do what you are proposing**. Plus, with databinding being so much more
usable in .Net, I fear you would be wasting your time.

However, you should probably be running this by the folks at
m.p.dotnet.framework.aspnet

Bob Barrows
* http://mvp.unixwiz.net/techtips/sql-injection.html
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=23

**
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls =GGLD,GGLD:2003-36,GGLD:en&q=asp%2Enet+database+CRUD+generat ors

http://www.codeproject.com/dotnet/spinvoke.asp

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

Re: What are your thoughts on this???

--____RQITDUWEMBJTKQWKRWLS____
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Bob,=20

It's already created and yes it uses stored procs, and passes parameters. =
No dynamic sql is generated. I'm just wondering how long I can put off =
"redeveloping" a similar app using .NET and using the current one for =
development projects. And how long I can use the classic ASP that the =
backend develops, hopefully forever... And yes, .NET expedites most of =
the stuff I've worked on in the past years, but I've gotten my money's =
work on these tools I've created:) =20

>>> Bob Barrows [MVP] 06/08/06 9:01 AM >>>

Shawn Ferguson wrote:
> I have created a application generator creates the add, delete,
> change, view database code and ASP code that will work for classic
> ASP and SQL Server 2000.

Similar to Eli Robillard's GenericDB?

> It has been an instrumental piece that has
> saved me NUMEROUS hours, all I have to do is give this application
> the fields, and viola... the ready working code is created.
>
> Now my problem is the future. I've pondered the idea of re-creating
> it in .NET which I hope to do when I get proficient at it, but in the
> mean time, do you think there will be any harm in future development
> if the administrative functions of a website system (add, delete,
> change fields) would function well in an environment that has .NET
> for the front end presentation. I'm thinking I can keep creating
> systems using the app generator, then just make the front end of the
> system, .NET'ified. THe only downfall is that the add, delete,
> change will be in classic ASP, but is that a downfall, and will
> classic ASP be around for awhile. Is this logical to you???
>
> Thanks!
>
If your application generator creates code that
1. Uses sql statements rather than recordsets to maintain data, and
2. passes values to the database via parameters,
then good for you. I think you may be doing a little too much processing
in the ASP (unless you tweak the generated code to use stored
procedures), but at least it is secure and relatively efficient
(compared to using recordsets for data maintenance, that is).

However, if your generator generates dynamic sql statements*, or uses
recordsets for database maintenance (as GenericDB does) then frankly I
think it should be scrapped. i created my first ASP app using GenericDB
and wound up rewriting it due to performance reasons.

The paradigm in .Net is completely different, and frankly, you would be
reinventing the wheel. There are class generators already written that
do what you are proposing**. Plus, with databinding being so much more
usable in .Net, I fear you would be wasting your time.

However, you should probably be running this by the folks at
m.p.dotnet.framework.aspnet

Bob Barrows
* http://mvp.unixwiz.net/techtips/sql-injection.html
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=3D23

**
http://www.google.com/search?sourceid=3Dnavclient&ie=3DUTF-8 &rls=3DGGLD,GGL=
D:2003-36,GGLD:en&q=3Dasp%2Enet+database+CRUD+generators

http://www.codeproject.com/dotnet/spinvoke.asp

--=20
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

--____RQITDUWEMBJTKQWKRWLS____
Content-Type: multipart/related; boundary="____MGHRRJMXKHOSXPEFVXXQ____"


--____MGHRRJMXKHOSXPEFVXXQ____
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable


>

Re: What are your thoughts on this???

Shawn Ferguson wrote:
> Thanks Bob,
>
> It's already created and yes it uses stored procs, and passes
> parameters. No dynamic sql is generated. I'm just wondering how
> long I can put off "redeveloping" a similar app using .NET and using
> the current one for development projects. And how long I can use the
> classic ASP that the backend develops, hopefully forever...

There've been several threads on this topic in the past week in this
group and in the asp.general group. Just browse for them.
The short answer is: don't worry about classic ASP breaking.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.